During the due diligence phase, the pursuit team would have conducted analysis of the engagement scope based on the limited accesses and information made available to them. The Knowledge Exchange Lead must now further conduct a detailed analysis to gain better understanding and refine the analysis received from the pursuit team. This will typically include analysis on quality, technology, Swift-Sustain, Volatility, EZTrans, CAST, complexity, stability and criticality with respect to Knowledge Exchange.

• Quality Analysis- This analysis helps to understand the stability of the system (in terms of code quality, script quality etc.) in order to estimate and forecast the expected volume of tickets for an application. If the expected ticket volume is higher than usual (indicating poor quality of build), the Knowledge Exchange duration will be more focused on application ticket history: frequently recurring issues, their resolution, peak periods of breakdowns, etc.

• Technology Portfolio Analysis (TPA)- It is applicable to Applications Maintenance (AM) services. It focuses on understanding the technology stack and helps to estimate the time it will take to perform Knowledge Exchange from an existing Client support group to an outsourcing support group on a portfolio of applications. The goal of TPA is to give Capgemini transition and delivery teams a way to guide Knowledge Exchange planning and to highlight applications/modules that should receive the most attention.

• Swift-Sustain- Applicable to application takeover, this method is based on FMEA(Failure Mode Effects Analysis) – however it focuses on corrective maintenance instead of preventive. Very early in the transition, as soon there is access to ticket history, the failure points from the past tickets are identified and the corrective actions / root causes for these failure points are determined.

• Volatility Analysis- It is performed using Volatility Analyzer tool or CAST tool. The objective is to identify any risk areas that need early planning and focus . It helps in focused transition, minimizes transition risks and provides inputs for application renovation phase. It identifies the most volatile components in the application code base & helps generate Knowledge Objects.

• EZTrans Analysis- EZTrans tools are in-house Capgemini standard tools for SAP and Oracle transitions. Engagement Manager (Transition) should check feasibility and benefit in respect to scope and duration of transition before deciding on using EZTrans tools.

• CAST Analysis- CAST tool will be run on the identified core (business critical) applications. The Engagement Manager (Transition)/ Delivery Manager  will check feasibility and benefit of CAST analysis in respect to scope of transition and duration of transition before deciding on doing CAST analysis. It helps plan for the service support based on type of applications that are going to be taken in.